Monitoring CPU and CPU Cores
Proactively monitor CPU and CPU Core usage on your Windows Servers with the Nodinite Windows Server Monitoring Agent. This guide shows you how to set custom thresholds, receive actionable alerts, and leverage real-time metrics to ensure optimal performance and prevent outages.
✅ Real-time monitoring of all CPUs and CPU Cores
✅ Customizable thresholds for performance and alerting
✅ Actionable alerts and remote actions to resolve issues fast
✅ Visualize CPU usage with charts and dashboard widgets
Learn how to monitor the utilization of your CPUs and CPU Cores and get alerts when the percentage used is too high over time
This page describes how Nodinite monitors CPUs using one or more role-based Monitor Views. Nodinite evaluates state based on user-defined thresholds, either global or specific. For managing CPUs, remote commands are available as Actions to help you swiftly resolve reported problems. The implemented Remote Actions are detailed on this page.
Example list of monitored CPU-related items in a Monitor View.
Monitoring Features
- Automatic Discovery
- The Nodinite Windows Server Monitoring Agent uses WMI to automatically discover CPU-related items. Sharing insights is easy within Nodinite using Monitor Views.
- State Evaluation - Based on user-defined thresholds (percentage over time)
- Category-based monitoring - Organize different types of CPU-related items; monitored Resources are grouped by Categories.
State evaluation for CPU-related items
The monitored CPU-related items are displayed within Nodinite as Resources. For example, if you have 1 CPU with 4 cores, you will have 5 Resources in Nodinite.
The name of the Resources comes from the count and index of the number of CPUs
- CPU => CPU Overall
- Core => CPU0, CPU1...
All monitored CPU items belong to one of the following 'CPU' Categories
Category Description CPU Make sure the CPU is running within user-defined monitoring thresholds CPU Core Make sure the CPU cores are running within user-defined monitoring thresholds 
List of CPU-related categories as a filter in Monitor View.The Application name is the Display Name from the configuration of the monitored Windows Server:
Example of Application naming pattern.
Each item (presented in Nodinite as a Resource), is evaluated with a state (OK, Warning, Error, Unavailable).
From within Nodinite, you can reconfigure the state evaluation on Resource level using the Expected State feature.
Note
Depending on the user-defined synchronization interval set for the Windows Server Monitoring Agent, there might be a delay before Nodinite Web Client/Monitor Views reflects the change. Click the Sync All button (or use the dropdown for individual agent selection) to force Nodinite to request a resynchronization.
Option to force Nodinite to request a resynchronization request with the Monitoring Agent.
Monitoring CPUs
For the CPU category, the monitored state evaluates as described in the table below:
| State | Status | Description | Actions | |
|---|---|---|---|---|
| Unavailable | Service not available | If the server can't be reached and evaluated either due to network or security-related problems | Review prerequisites | |
| Error | Error state raised | The 'CPU' is using too much resources for too long time | - | |
| Warning | Warning state raised | Not yet implemented | - | |
| OK | Online | The 'CPU' is accessible and is within user-defined monitoring thresholds | CPU Chart Edit |
Actions for CPU
The following Remote Actions are available for the CPU and CPU - Core Categories:
Remote Actions available for the CPU category.
Edit thresholds
You can manage the alert thresholds for the selected CPU/CPU Core Resource; simply click on the Action button and then click the Edit thresholds menu item within the 'Control Center' section.
Edit thresholds, using the 'Edit' action.
Next, click the option to present the modal.
'Edit thresholds' modal for CPU Monitoring.
The CPU Core section is not enabled by default; you can expand the accordion to view and manage the Monitoring thresholds.
'Edit thresholds' accordion for CPU Core Monitoring.
Metrics chart: Metrics
You can view statistics about the selected CPU instance by clicking the Action button and then the CPU Chart menu item within the 'Control Center' section.
Show CPU statistics, using the 'CPU Chart' action.
Next, click the option to present the modal.
Example of CPU usage statistics.
This modal is designed to be used as a Widget in the Dashboard.
CPU statistics example as a Widget on the Dashboard.
Monitoring CPU Cores
Monitoring CPU Cores is a more fine-grained monitoring option compared with CPU Monitoring. All monitoring options are the same, so the previous documentation above for monitoring CPUs covers this topic.
Configuration
Use the Remote Configuration to manage the CPU configuration.
CPU tab
Click the CPU tab to manage CPU Monitoring options.
Example of the 'CPU' tab.
There are multiple options for Monitoring the CPU. Two major subcategories exist:
- CPU
- CPU Core
CPU
- Enable CPU Monitoring - When checked, enables the Monitoring of the 'CPU Overall' usage. Otherwise, Monitoring is disabled.
- CPU Warning Threshold % - When the CPU usage exceeds this threshold for more than the configured number of seconds (CPU Duration), the evaluated state is 'Warning'.
- CPU Error Threshold % - When the CPU usage exceeds this threshold for more than the configured number of seconds (CPU Duration), the evaluated state is 'Error'.
- CPU Threshold overrun duration - The maximum allowed duration breaching the threshold (seconds).
CPU Core
- Enable CPU - Core Monitoring - When checked, each Core in the CPU(s) will be monitored individually for this Windows Server
- CPU Core Warning Threshold % - When the CPU Core usage exceeds this threshold for more than the configured number of seconds (CPU Core Duration), the evaluated state is 'Warning'.
- CPU Core Error Threshold % - When the CPU Core usage exceeds this threshold for more than the configured number of seconds (CPU Core Duration), the evaluated state is 'Error'.
- CPU Core Duration - The maximum allowed duration breaching the threshold (seconds).
Next Step
Related Topics
Windows Server Monitoring Agent
Resources
Monitoring
Monitor Views